An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi, I can sign in to my Apple ID, but my Apple Developer account shows a “closed” status and I’m unable to access App Store Connect features. My app is currently showing “Ready for Distribution,” so the account appears active, but developer access is restricted. I’ve already contacted Apple Developer Support and am waiting for their response. Also, I temporarily can’t access my primary email due to a verification issue, so I’ve provided an alternate contact email and phone number in my support request. Has anyone experienced a similar situation or knows possible reasons for a “closed” developer status while the app remains approved? Thanks.

Hello! I submitted a new version of my app for review yesterday, and the status has been stuck on In Review for over 26 hours. In our previous updates, the review process was much faster. It is very important for us that this review does not get delayed further as it contains critical compliance updates for Guideline 5.3.4. My App Apple ID: 6761430958 Thank you in advance for any advice or investigation!

Hi everyone, I am looking for some insight from anyone who has dealt with a long "In Review" session recently, especially for apps in complex categories like prediction markets or finance. The Situation: Our app was previously rejected under Guideline 5.3.4 (Gambling/Prediction Markets). We submitted a formal appeal with a very detailed compliance brief and a comprehensive demo video to show our non-custodial architecture. The build went "In Review" exactly 24 hours ago. This is a standard (non-expedited) submission, but since the status hasn't moved in a full day, I wanted to see if this is common for apps that are under "compliance audit." App Details Name: Clover: Predict with Friends App ID: 6761430958 Bundle ID: fun.clover.app Version: 1.2.0 (Build 19) Status: In Review (24+ hours) What we have already tried Confirmed there are no unread messages in the Resolution Center. Verified that all testing credentials and demo videos are functional. Filed a formal App Status Inquiry via Developer Support. Questions for the community For those in "gray area" categories (prediction, crypto, etc.), how long does your "In Review" phase typically last for a standard submission? Given the 5.3.4 context, does a 24-hour session usually mean it's being escalated to a more senior reviewer or a legal lead? Is it common for standard reviews to stay "In Review" across a weekend or multiple business days? I would love to hear from anyone who has navigated a similar deep dive review. Thank you for any advice or shared experiences!

Hi everyone, I am developing an app for a sport event in my area, which would provide live updates and notifications to participants and viewers, the event is coming up in 3 days and I thought I'd be able to have the app ready in the App Store by now, given the "on average, 50% of apps are reviewed within 24 hours and over 90% of apps within 48 hours" in the initial email message. Unfortunately, since a week ago where I uploaded my first version, it has been stuck in "Waiting for Review". I sent an expedited review request, but that did not seem to change anything. Looking through the forum I have been able to see others having the same issue, I'd appreciate it if someone from Apple could look into this and tell me why the review is stuck, if there's anything I need to do from my end. App ID: 6764243507 Thank you!

I submitted an app update for review yesterday and got rejected on the same second the app went to "In Review": In Review: Date: Mon, 4 May 2026 23:19:24 +0000 (GMT) From: App Store Connect App Crash Rejection email: Date: Mon, 4 May 2026 23:19:24 +0000 (GMT) From: App Store Connect No crash log, no device information. 20 TestFlight testers with no crashes and we tested on a range of devices and iOS versions as well. I replied to the review asking for the crash log and device information. But was it a custom to have the crash log and device information attached to the crash rejections? The first one for us, so we are not sure. We are re-testing and fixing speculatively the risk points. But same second In Review > Rejection with crash reason with no crash log and no device information, looks very strange to us.

Hello everyone, my initial app release (Version 1.0) has been stuck in the 'Waiting for Review' status for 6 days now. It is a comprehensive app that includes localization for 14 different languages. I understand that initial submissions and extensive localizations can take longer to review, but 6 days seems unusually long. Is anyone else experiencing similar extended delays with App Review recently? Any insights would be appreciated. Thank you.

Hello everyone, I’m posting again because the situation is still not resolved, and at this point we have been unable to pass App Review for almost 3 weeks. Here is the full timeline: We originally submitted the app for review and waited almost 2 weeks while it stayed in “Waiting for Review.” Since there was no progress, we cancelled that submission and submitted a new build, hoping it might help. After resubmitting, we waited about another week again in “Waiting for Review.” Then, after posting here on the forum, the app finally moved to “In Review.” However, it has now been stuck in “In Review” for 2 days, with no updates, no rejection, and no request for additional information. We have contacted Apple Developer Support multiple times, but we mostly receive generic responses and promises to wait. Unfortunately, we still don’t have any clear explanation of what is happening or what we can do to help move the review forward. We understand that review times can vary, but the total delay is now close to 3 weeks, and this is creating serious problems for our release. We don’t know whether there is a technical issue, a queue issue, or something specific blocking the review. App ID: 6761535196 Could someone from Apple please check whether the review is stuck or if there is anything required from our side? Any advice from developers who experienced something similar would also be very helpful. Thank you.

I've exhausted standard channels and we're at the point where this delay is creating real financial harm for our business and our customers. App ID: 6761686513 Our initial submission was reviewed within 2 hours and we received feedback. We addressed every item in the rejection, resubmitted, and the app has now been sitting in "Waiting for Review" for with no movement. We submitted an expedited review request, contacted Apple Developer Support by phone, and emailed. None of which have produced a clear answer or estimated timeline. Today, May 1st, was our planned hard launch. We have hundreds of paid subscribers: small business owners who specifically scheduled their first billing cycle to begin on launch day so they could use the platform's full feature set, including the iOS app, from day one. Our app supports their booking system, payment processing, client management, and day-to-day operations. Because the app didn't get approved in time: We had to issue full refunds to every subscriber charged today, since they're paying for a product they can't fully use. Our subscribers are now in limbo. They've already onboarded their clients onto our system and are running their businesses through it, but the iOS experience that was promised at launch isn't available. Each additional day of delay compounds this. Our small team is fielding messages from subscribers asking when the app will be live, and we don't have an answer to give them because we don't have one ourselves. I understand review times vary and the queue is real, and I'm not trying to jump the line unfairly. But the advised 24–48 hour window hasn't held this round. Our initial review came back the same calendar day we submitted, and we resubmitted within hours of receiving the feedback. We're now far past that original turnaround with no signal that anything is moving, and no response from expedited review or Developer Support to indicate where we stand. If anyone from Apple sees this and can take a look at App ID 6761686513. I'd be incredibly grateful. Happy to share any other detail that helps. We just want to get unstuck. Thank you.

Hello, I've been trying the last week trying to get my app approved for the App Store. It's my first app and I'm not really sure what's going on. My app is getting rejected due to "App Completeness". Here's the rejection message: App Review Guideline Issue This is an automated message. The review of this submission cannot proceed. See below for more information. The app crashed after the initial launch. Apps that crash negatively impact users. Test the app on supported devices to identify and resolve crashes and stability issues before resubmitting for review. Learn more about testing a release build. When we submitted the first time we got rejected because our Apple sign in did not auto fill the user's name and we didn't have the EULA Link in the description. So the app didn't crash here as a tester sent screenshots and was in our app. We resubmitted and then we started getting these crashes. I examined the code we added from the first revision and tested the start up and everything worked fine on ours and our 30+ beta testers end. The thing is we're not getting a crash log from Apple testers or Apple's automated tester (if automated testing exists?). We are creating a fitness app that implements HealthKit. We have the required HealthShare and HealthUpdate messages in the signing and capabilities of our target. I'm not sure this would be the issue since the app actually executed the first run though. I've researched and some articles did say long load times on bad internet could make iOS terminate an app. So we worked to get our initial load network calls down from 10 seconds to about 1-2 seconds. This did not work either. We are using SwiftData to cache exercises fetched from our backend locally but we haven't made any changes to the entity's. So I wouldn't expect bad data to cause a crash especially because we flush even if it were bad data anyway. I've ran with instruments to see if this was a memory issue: With an Authed User with data loaded it gets to about 33MiB With a fresh install memory usage is about 17MiB I did have a point of interest in my profile: api.revenuecat.com is not listed in your app’s NSPrivacyTrackingDomain key in any privacy manifest. It may be following users across multiple apps and websites to create a profile about users of apps that contact this domain. I don't use revenue cat for tracking for Ads so I probably shouldn't add it to the NSPrivacyTrackingDomain right? I'm really lost here any advice would be much appreciated. I guess my questions are if Apple has an automating testing environment how can I closely match that for testing on my end? If this is an actual tester why am I not getting a crash log or steps to repeat this issue? Has anyone else experienced the pain I'm currently suffering?

Hello Apple Developer Community, We are very excited to release our first apps on the App Store. I wanted to kindly ask for guidance because our first submissions appear to be taking longer than expected, and we want to make sure there is nothing missing or blocking the review process from our side. Our first app has been waiting for more than 15 days in total. App ID: 6761379839 Latest Submission ID: 8e767ece-a348-469a-9230-7e695e84ca44 After we first submitted the app, it entered review on the first day. App Review then requested a screen recording / walkthrough video. We prepared and submitted the requested screen recording immediately. After that, the submission did not appear to move forward for an extended period. While waiting, we continued development and completed a newer version of the app. Since the older submission had not progressed, we removed the previous build and submitted the newer version with an updated screen recording. One thing we noticed is that the subscription and in-app purchase products for this app appear to be “In Review.” We are not sure if this is expected behavior because the app version itself still appears to be waiting, or if there may be some kind of dependency or review state issue causing the submission to remain stuck. We also contacted Apple Developer Support regarding this situation. Case ID: 102882849875 We have another app on the same account that is also waiting for review. App ID: 6762281533 Submission ID: 0e4b607e-9e28-4d13-9c2a-98afe8c2e9aa This second app has been waiting for around 3 days. Could someone please advise or help us. Thank you very much.

Hello Everyone, For the second time in 3 months, I am seeing my app getting stuck in 'Waiting for review' state for weeks. I wrote to apple support and got an email 11 days ago saying they have initiated expedited review of the version review. But still I see no progress with the review and status is still waiting for review. I sent emails 2-3 times after that but no response. Did anyone else face this and what else can I do now? Thanks

Hello, I am seeking advice or assistance regarding a significant delay in the review process for my app, Preppy (App ID: 6443527187). The app has been on the App Store for over 4 years and has been featured as "App of the Day" on three separate occasions. We have always maintained a good standing, but we are currently facing an unprecedented bottleneck that is negatively impacting our users. The Timeline: Version 2.6: Approved successfully ~3 weeks ago. Version 2.6.1: Submitted shortly after to address a critical bug. It was rejected due to the screenshots (which were the same as in 2.6), but I changed them according to the feedback. It remained in review for another 7 days. Even after requesting an expedited review, there was no movement anymore. Action taken: I rejected the build and resubmitted with a new build and updated screenshots again, hoping it would help. It sat for another 5 days with no status change again. Phone Support: I spoke with support via phone and was advised to increment the build/version number and resubmit and was told the app is in the expedited queue, so it will be reviewed shortly, which did not happen. Version 2.7: Uploaded 4 days ago with a new version number, updated screenshots yet again, and an improved description. It has been stuck in "Waiting for Review" since then. I have sent multiple emails to the App Review team explaining that this update contains a critical bugfix. Because of this delay, we are now receiving a wave of negative 1-star reviews from users who are experiencing the bug that is already fixed in the pending build. I have had no response to my follow-up emails, and the "Contact Us" forms haven't resulted in any updates. Has anyone else experienced this recently with a long-standing app? Is there any other way to escalate this beyond the standard expedited review form (which has already been used)? Thank you for any help or guidance.

Hi everyone, I’m looking for some guidance regarding my app review status. About a week ago, I submitted my app for review on the App Store. The review team responded asking for some declarations and a few changes in the app. I addressed all the requested changes and resubmitted the app promptly. However, it has now been more than a week since the resubmission, and I haven’t received any further updates or feedback from the review team. The status still appears unchanged, and there has been no communication. I understand that review times can vary, but I wanted to check: Is this delay normal after a resubmission? Is there anything I should do from my side (e.g., follow-up, resubmit again, contact support)? Has anyone else experienced similar delays recently? my app name is Darenite Any insights or suggestions would be really helpful. Thanks in advance!

Hi Apple Team, I'd like to seek here some answers if 70 hours of Waiting for review is normal? I already open a ticket today but seems like I need to wait for another 48 hours or way more than that again. Apple ID: 6764268650

Hi all, We are developing an iOS app that includes private user-to-user chats, commercial offer details with monetary value, and customer identification data. In line with OWASP MASVS-PLATFORM-3 requirements regarding unintentional sensitive data exposure, we need to protect these specific screens from screenshots and screen recording. We have carefully reviewed the relevant App Review Guidelines (2.5.1 on public APIs, 2.5.2 on self-contained bundles, 5.1.1 on privacy) and the related Human Interface Guidelines. From this analysis we have observed the following: iOS does not expose a public API to globally disable screen capture (no direct equivalent of Android's FLAG_SECURE). The SwiftUI .privacySensitive() modifier is effective for Lock Screen widgets and Always-On Display, but it does not appear to prevent screenshots or screen recording of an app's main UI while in the foreground. A number of widely distributed App Store apps (banking, authenticator, secure messaging) implement some form of screenshot protection on sensitive screens. Several established open-source libraries leverage the system behavior of UITextField with isSecureTextEntry as a wrapping container for arbitrary views, in order to achieve pixel-level protection for sensitive content. We would appreciate clarification on the following points: For privacy-driven protection of sensitive screens (private chats, customer data, monetized offers), is there an officially recommended approach we may have missed? Are there public APIs intended specifically for this use case beyond .privacySensitive()? Is the practice of leveraging UITextField with isSecureTextEntry as a wrapping container for arbitrary views considered an acceptable use of public APIs under Guideline 2.5.1, or does it carry App Review risk? Are there official recommendations or documentation for apps handling sensitive personal data that wish to align with industry standards such as OWASP MASVS-PLATFORM-3 for screenshot and screen recording leakage prevention? The intended use is strictly limited to a small number of screens marked as containing sensitive data (private messages, deal details, customer information). The protection would be selective and clearly communicated to the user via in-app messaging, not global to the app. Thanks in advance for any clarification, including pointers to existing documentation or threads we may have missed. Deployment target: iOS 15+

Hi everyone, I’m currently stuck with a blocking issue in App Store Connect and would really appreciate any guidance or insight. Issue: My app version (iOS App 1.0) is missing the “In-App Purchases and Subscriptions” section entirely. Because of this, I cannot attach my subscriptions to the version, which is preventing me from submitting the app for review. Additionally, I also do not have the option to create a new version, so I can’t work around the issue by moving to 1.0.1. What happened before this: I uploaded a build (Build 24) Submitted the app for review Then removed the submission After that, the IAP section disappeared completely Since then, I cannot attach subscriptions or create a new version Current state: Subscriptions are created and show “Waiting for Review” New Build is attached to Version 1.0 All metadata and screenshots are complete “In-App Purchases and Subscriptions” section is missing “Add Version” option is not available What I’ve tried: Removing and re-adding the build Waiting for UI refresh/processing Contacting Apple Developer Support (case has been escalated for 6 days with no response) Impact: This is currently blocking my app launch because I would be rejected since the subscriptions are not linked, as I cannot submit my first subscription with the app. Questions: Has anyone experienced a missing IAP section after removing a submission? Is there any way to force reset the app version state from the developer side? Is this a known App Store Connect issue? Any help or suggestions would be greatly appreciated. Thanks in advance.

Hi Apple Team, I would like to ask if it is normal for the “Waiting for Review” status to take 70 hours. I have already opened a ticket today, but it seems I may need to wait another 48 hours or possibly longer. Apple ID: 6764268650

Hi everyone, I’m currently experiencing an issue where my auto-renewable subscriptions are not loading during TestFlight and App Review. Setup: iOS app using StoreKit 2 + RevenueCat Subscriptions: Weekly Monthly Both are configured in: App Store Connect (attached to app version) RevenueCat (entitlement + offerings + packages) Current Status: Subscriptions show: “Waiting for Review” in App Store Connect Paid Apps Agreement is Active Banking + tax info is completed ⸻ What’s happening: In TestFlight → Paywall loads but: Products stay in loading state Prices never appear During App Review: Apple rejected with: “Unable to load plans” ⸻ Debug Info: RevenueCat logs confirm: Offerings are fetched successfully $rc_weekly and $rc_monthly packages exist However, StoreKit does not return product pricing in TestFlight ⸻ Question: Is this expected behavior when subscriptions are still in “Waiting for Review”? Or should products still fully load in sandbox/TestFlight even before approval? ⸻ What I’ve already verified: Subscriptions attached to app version ✅ Offerings configured in RevenueCat ✅ Product identifiers match exactly ✅ Using real device (not simulator) ✅ ⸻ Goal: I want to ensure: Subscriptions load correctly during App Review App is not rejected again for “Unable to load plans” Any guidance would be greatly appreciated 🙏

Our app update has been stuck in “Waiting for Review” for more than 8 days, and it appears the submission may have been overlooked or affected by a system issue on Apple's system. App ID: 1600450223 Bundle ID: com.asbing.woomanager Version: 5.3.1 What we’ve already tried: Requested an Expedited App Review Contacted Developer/App Review Support, but received no response (Case ID: 102878632497) Cancelled and resubmitted the update, but it remains in “Waiting for Review” for several days Could you please confirm whether this update is still in the review queue or if any issues are blocking the review? This is a critical release for us, and despite multiple attempts, we have been unable to resolve the issue.

Hello App Review Team, I’m reaching out regarding my first app release, Smala. App ID: 6762228514 Bundle ID: SmalaApp.Smala The app has now remained in Waiting for Review status for 8 days. I also submitted an expedited review request, which was approved, but the status has still not changed. This delay is creating significant launch issues for our team, as this release is time-sensitive. We would sincerely appreciate any assistance or status update when possible. Thank you very much for your time.